/test pj-rehearse

@petr-muller the e2e-aws and launch-aws tests are failing to start up a cluster. This has been happening since yesterday. Am I messing something up or is this just test flakes?
The config and job match what we have for cri-o 1.13 in #3962 and those tests are passing.

/test pj-rehearse

@umohnani8 I don't know. The rehearsals execute the added/changed jobs as if they were run against the target branch HEAD, so in the case of e2e tests their results depend on how healthy openshift currently is. It's certainly known to flake a bit (current build cop usually knows if there's currently something going on). The rehearsals do not block the merge, so if it looks like the jobs work fine and the tests inside flake them, you can merge them.

/test core-valid
/test core-dry

@petr-muller got it, thanks! Trying to debug the problem here, seems something is off with the cri-o being built for the ci.

/test pj-rehearse

Look at the log bundle and drill down into one of the master's journals:

Jun 19 13:13:46 ip-10-0-129-84 hyperkube[944]: F0619 13:13:46.174808     944 server.go:264] failed to run Kubelet: failed to create kubelet: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial unix /var/run/crio/crio.sock: connect: no such file or directory"

And that's because:

-- Logs begin at Wed 2019-06-19 13:09:22 UTC, end at Wed 2019-06-19 13:41:43 UTC. --
Jun 19 13:13:43 ip-10-0-129-84 systemd[1]: Starting Open Container Initiative Daemon...
Jun 19 13:13:44 ip-10-0-129-84 crio[928]: time="2019-06-19 13:13:44.541376996Z" level=fatal msg="config validation: invalid plugin_dirs entry: stat /var/lib/cni/bin: no such file or directory"
Jun 19 13:13:44 ip-10-0-129-84 systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE
Jun 19 13:13:44 ip-10-0-129-84 systemd[1]: crio.service: Failed with result 'exit-code'.

/test pj-rehearse

@umohnani8: The following test failed, say /retest to rerun them all:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

@smarterclayton @stevekuznetsov ptal. This is ready.

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stevekuznetsov, umohnani8

The full list of commands accepted by this bot can be found here.

The pull request process is described here

@umohnani8: Updated the following 3 configmaps:

• job-config-misc configmap in namespace ci using the following files:
  • key cri-o-cri-o-release-1.14-presubmits.yaml using file ci-operator/jobs/cri-o/cri-o/cri-o-cri-o-release-1.14-presubmits.yaml
• ci-operator-misc-configs configmap in namespace ci using the following files:
  • key cri-o-cri-o-release-1.14.yaml using file ci-operator/config/cri-o/cri-o/cri-o-cri-o-release-1.14.yaml
• ci-operator-misc-configs configmap in namespace ci-stg using the following files:
  • key cri-o-cri-o-release-1.14.yaml using file ci-operator/config/cri-o/cri-o/cri-o-cri-o-release-1.14.yaml